Robustify yaw emergency estimator against GNSS glitches #23894
+17
−24
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The likelyhood can be really small when the innovation is suddenly large. This can occur during a GNSS velocity glitch and shouldn't reset the filter as it would bring it back to a really vulnerable state.
bresch
force-pushed
the
pr-ekf2_yaw_est_no_reset
branch
2 times, most recently
from
2a4d648
to
fdb1248
Compare
bresch
force-pushed
the
pr-ekf2_yaw_est_no_reset
branch
from
fdb1248
to
55001a4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved Problem
When a GNSS velocity glitch occurs, the likelihood of all the estimators go to 0, driving all the weights to 0 that triggers a reset of the estimator. This makes the estimator really vulnerable as it would immediately converge to the incorrect GNSS readings. Since the main EKF requires a valid yaw emergency estimate at this time to see if the sudden large velocity innovation can be due to an incorrect heading it could cause a false yaw emergency reset (to an incorrect value!).
Solution
Tested in replay:
